Skip to main content

This is a new service – your feedback will help us to improve it.

Newcastle-under-Lyme Borough Council

Tree preservation zone

There is a problem

  • tree-preservation-order column must match the reference field in the tree preservation order dataset

entity: 19206098

reference
T7-9\TPO0009_A1
name
tree-preservation-order

undefined

T7-9\TPO0009
tree-preservation-zone-type
area
geometry
MULTIPOLYGON (((-2.379445 52.923068,-2.379363 52.923087,-2.379174 52.923124,-2.379060 52.923136,-2.378946 52.923141,-2.378840 52.923136,-2.378745 52.923108,-2.378713 52.923056,-2.378685 52.923004,-2.378637 52.922964,-2.378482 52.923010,-2.378363 52.923034,-2.378145 52.923081,-2.378122 52.923084,-2.378045 52.923086,-2.377951 52.923085,-2.377936 52.923081,-2.377896 52.923061,-2.377791 52.922937,-2.377729 52.922889,-2.377734 52.922870,-2.377588 52.922699,-2.377515 52.922607,-2.377458 52.922568,-2.377402 52.922554,-2.377054 52.922531,-2.377037 52.922471,-2.377039 52.922415,-2.377046 52.922362,-2.377082 52.922362,-2.377177 52.922371,-2.377188 52.922302,-2.377211 52.922235,-2.377246 52.922178,-2.377292 52.922142,-2.377390 52.922083,-2.377465 52.922042,-2.377655 52.921985,-2.378039 52.922358,-2.378055 52.922355,-2.378067 52.922332,-2.378025 52.922286,-2.377857 52.922128,-2.377737 52.922019,-2.377684 52.921977,-2.377587 52.921910,-2.377452 52.921820,-2.377218 52.921671,-2.377084 52.921594,-2.376825 52.921456,-2.376798 52.921445,-2.376791 52.921443,-2.376734 52.921452,-2.376590 52.921493,-2.376375 52.921570,-2.376410 52.921598,-2.376552 52.921664,-2.376695 52.921723,-2.376829 52.921787,-2.376869 52.921820,-2.376877 52.921861,-2.376865 52.921894,-2.376709 52.922042,-2.376604 52.922149,-2.376521 52.922116,-2.376497 52.922059,-2.376355 52.922081,-2.376098 52.921949,-2.375964 52.922034,-2.375985 52.922070,-2.376003 52.922116,-2.376017 52.922144,-2.376032 52.922206,-2.376046 52.922245,-2.376068 52.922340,-2.376068 52.922384,-2.376070 52.922406,-2.376063 52.922463,-2.376051 52.922508,-2.376032 52.922550,-2.376025 52.922573,-2.376009 52.922600,-2.376003 52.922613,-2.376003 52.922643,-2.376016 52.922700,-2.376027 52.922758,-2.376033 52.922780,-2.376114 52.922843,-2.376118 52.922850,-2.376121 52.922858,-2.376121 52.922867,-2.376119 52.922875,-2.376101 52.922910,-2.376101 52.922921,-2.376122 52.922993,-2.376145 52.923087,-2.376156 52.923119,-2.376165 52.923141,-2.376176 52.923162,-2.376232 52.923253,-2.376260 52.923293,-2.376290 52.923331,-2.376382 52.923421,-2.376437 52.923467,-2.376575 52.923570,-2.376935 52.923744,-2.376931 52.923748,-2.377074 52.923809,-2.377308 52.923917,-2.377275 52.923932,-2.377422 52.924008,-2.377425 52.924009,-2.377445 52.923979,-2.377537 52.924021,-2.377547 52.924031,-2.377625 52.924091,-2.377641 52.924096,-2.377609 52.924102,-2.377714 52.924156,-2.377730 52.924158,-2.377773 52.924171,-2.377852 52.924147,-2.377956 52.924112,-2.378013 52.924098,-2.378083 52.924034,-2.378176 52.924048,-2.378244 52.924090,-2.378634 52.923942,-2.378630 52.923920,-2.378548 52.923908,-2.378426 52.923906,-2.378305 52.923912,-2.378288 52.923883,-2.378275 52.923847,-2.378276 52.923839,-2.378282 52.923825,-2.378294 52.923813,-2.378283 52.923794,-2.378259 52.923765,-2.378219 52.923736,-2.378320 52.923710,-2.378659 52.923586,-2.378705 52.923574,-2.378729 52.923553,-2.378867 52.923500,-2.378926 52.923505,-2.379080 52.923583,-2.379279 52.923646,-2.379345 52.923722,-2.379614 52.923641,-2.379620 52.923634,-2.379623 52.923593,-2.379622 52.923481,-2.379590 52.923403,-2.379574 52.923341,-2.379573 52.923267,-2.379533 52.923201,-2.379481 52.923139,-2.379445 52.923068)))
point
POINT (-2.377427 52.923011)
notes
entry-date
2026-07-28
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Newcastle-under-Lyme Borough Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL